Conversation
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
| request.log.error(err, 'Error occurred!') | ||
| res.status(500).send('Internal Server Error') | ||
| } | ||
| } |
There was a problem hiding this comment.
Bug: Middleware Order Causes Error Handling Failure
The errorMiddleware tries to use req.log for error reporting. However, loggingMiddleware is placed after express.json(). If JSON parsing fails, req.log won't be initialized, leading to a TypeError when the error handler attempts to access req.log.error().
Additional Locations (1)
2 participants
Summary
/connector-healthendpointkafka-connectserviceImplementation Details
Created a new standalone service
kafka-connect-monitorthat:localhost:8083to fetch connector statuses/health